home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
xlax_253.arc
/
XLAXNODE.DOC
< prev
next >
Wrap
Text File
|
1991-09-28
|
77KB
|
1,927 lines
XLAXNODE II
Version 2.53
Program and Documentation
Copyright 1987-1991
By Scott Samet
Friends of Dorothy
Fidonet 1:135/990
XLAXNODE II - Version 2.53 Page 2
What does it do?
XlaxNode is a nodelist processing utility designed to replace many of
the existing utilities with a single step. It will produce any or all
of the following files in one pass:
Opus 1.0x: NodeList.Sys and NodeList.Idx*
Opus 1.1x: NodeList.Dat and NodeList.Idx*
Opus 1.7x: NodeX.Dat, NodeX.Ndx, Sysop.Ndx
Binkley 2.50: NodeList.Ext and NodeList.Idx*
including POINT support
NodeX.Dat, NodeX.Ndx, Sysop.Ndx
QuickBBS: QNL_DAT.BBS and QNL_IDX.BBS (including
Pursuit processing and the "Binkley
Extensions")
QuickBBS 2.75: NodeIdx.DAT and NodeInc.DAT. See
"QuickBBSIndex" for details.
TBBS/Seadog: NodeList.Dog, NetList.Dog and Index.Dog
Userlist.Dog for Seadog 4.5
FrontDoor 1.99c/ Nodelist.FDX, FDNode.FDA**, Phone.FDX,
FrontDoor 2.0: Phone.FDA, Userlist.FDX, Password.Sys and
FDNet.PVT
TPBoard 5.0: NodeList.TPB and NetList.TPB
Remote Access 1.00: NodeIdx.RA and NodeInc.RA. See "RALIST"
for details and restrictions.
Silver Xpress 3.0: XPNLV1.IDX, XPNLV2.IDX and XPNLV2.DAT
* A single NodeList.Idx may be shared by all three files.
** Users of earlier versions should rename this file to NodeList.FDA
XLAXNODE II - Version 2.53 Page 3
In addition, it will produce the following files that are not specific
to a particular system:
NodeList.Fon RouteGen work file
FidoUser.Lst User Name lookup file
NodeList.BBS Time honored FidoNet Nodelist
NodeList.DLM Delimited for Spread Sheet or Database
import
The following files are optimized for interface with Opto-Isolated
Carbon-based Biochemical Systems:
NodeList.Prn 132 columns wide (index optional)
NodeList.Txt 80 columns wide (index optional)
NodeList.Dbl 80 columns, two lines per node (index
optional)
NodeText.BBS 80 columns, no pagination, for on-line
viewing
Coord.nnn 80 columns, Zone, Region and Net
Coordinators
The program will do the processing required to support PC Pursuit
scripts for FD, Opus and Binkley. It will also Prune the nodelist,
selecting the desired Zones and Nets.
What doesn't it do?
XlaxNode is designed as a FidoNet utility. Nodelists produced by
other networks should be processed correctly if they conform to
FidoNet Technical Standards Document FTS-0005. Non-conforming
nodelists may produce unpredictable results (in other words, you may
not like the output).
Page 4 XLAXNODE II - Version 2.53
LICENSE
DISTRIBUTION:
You may distribute the program on magnetic media or via modem,
provided you distribute the original, unaltered archive. You may
repack and change the file type to reflect the use of another
archive utility (PAK, ZOO, DWC, etc.). You may not alter, add or
delete anything within the file.
This program is distributed in combination with its companion
program, XlaxDiff, as a single file. If you received one without
the other, someone has violated the distribution license.
USE:
You may use this program for a thirty day evaluation period
without charge. After the evaluation period, you are expected to
pay the license fee or discontinue using the program.
During the evaluation period, the program will request keyboard
input each time it is invoked. After installation of the
license key, the program will operate without intervention. It
can then be used in an unattended batch file.
WARRANTY
This program is distributed on an as-is basis. You have a thirty day
evaluation period to decide if it operates to your satisfaction.
EXCEPT AS PROVIDED ABOVE, AND SUBJECT ANY CONTRARY PROVISIONS OF
APPLICABLE STATE LAW, ANY AND ALL IMPLIED WARRANTIES, INCLUDING
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
AND ANY WARRANTY COVERAGE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES ARE
HEREBY DISCLAIMED. IN NO EVENT SHALL DAMAGES EXCEED THE LICENSE FEE
PAID.
If you have suggestions or problems, before or after licensing, please
follow the problem reporting procedures found at the end of this
document.
XLAXNODE II - Version 2.53 Page 5
XLAXNODE LICENSE FORM
To: Scott Samet
PO Box 162082
Miami, FL 33116-2082 USA
Name: ____________________________________________________________
Address: ____________________________________________________________
____________________________________________________________
City: ____________________________ State: ________ Zip: ________
Country: ____________________________
The license fee covers operation of XlaxNode and XlaxDiff for the
node(s) listed below.
Copy the node numbers from the NODE statement of your XLAXNODE control
file. Do NOT include AKA addresses.
(1) _______________ (2) _______________ (3) _______________
Number of nodes listed: _________ at $15 each $ _________
License Key Delivery
US (APO/FPO) and Canada: no charge
International: $5/order $ _________
Total Enclosed: $ _________
All orders MUST be prepaid:
By Check or Money order in US Dollars on a US Bank
-or- Canadian Post Office US Dollar Money Order
Send Cash at your own risk
Purchase orders, Credit cards, foreign checks, giros and other
payment forms cannot be processed and will be returned.
Allow two weeks for domestic delivery, three weeks for international
delivery.
Page 6 XLAXNODE II - Version 2.53
OPERATION
There are some differences between this program and the program(s) you
are probably using. You may get an error message or even different
results. Take a time to read the docs and avoid problems.
By default, this version uses IBM PC BIOS calls for the video display.
The -G switch on the command line will force the use of ANSI escape
sequences. Machines without PC BIOS compatibility, such as the Z-100
or DEC Rainbow MUST use the -G switch.
When used under DOS 2.x, the EXE file must reside in the current
directory; the DOS PATH will not suffice.
By default, the program will look for a file named XLAXNODE.CTL in the
current directory. This can be overridden by using -Cfilename on the
command line.
XLAXNODE.CTL is a standard ASCII text file. Each control statement is
entered on a separate line. A semi-colon causes the rest of the line
is to be treated as comments. Blank lines or lines starting with
semi-colons are also comments. No line, even a comment line, may
exceed 255 characters in length.
You may augment or override commands in the control file by placing
them on the DOS command line. Commands that require arguments must be
enclosed in ASCII quotes ("). The COST and DIAL commands require
multiple lines and cannot be placed on the DOS command line. For
example, if you are running a temporary modem at 1200 baud, you might
enter:
XLAXNODE "MAXBAUD 1200"
Command line arguments are treated as if they were included at the end
of the control file.
If an error occurs during processing, XlaxNode will terminate and
return an error code that can be tested in the batch file. Error
codes and their causes are:
0 Normal completion, no errors.
1 No output files enabled.
2 CRC Error in input nodelist.
5 Not enough memory to continue.
6 No NODELIST.nnn file found to process.
7 Error in a control statement.
8 Attempt to open a file failed.
9 Sort or Disk I/O Error occurred.
XLAXNODE II - Version 2.53 Page 7
COMMANDS
INCLUDE filename
Defines an auxiliary file containing XlaxNode Control statements.
XlaxNode will read and process the named file, then continue with
the next statement in the current file. Include files may be
nested, subject to available memory and file handles.
NODE <zone>:<net>/<node>
This is REQUIRED. It must be the first statement of the control
file. Enter the primary node number of the system on which the
compiled nodelist will be used. Do not enter AKA addresses.
Example:
NODE 1:234/567
SORTWORK [path\]filename
If a sort cannot be completed in memory, a disk work file will be
created and deleted when no longer needed. SORTWORK controls
where the file will be placed. An Extended or Expanded Memory
ramdisk is an ideal place for this file. If this statement is
omitted, the file will be created in your current directory. The
VERSION7, SEADOGLIST, FDLIST, SINDEX, and USERLIST/INTERLIST
options trigger sorts, although only the user lists are likely to
overflow to disk.
BUFFERS <number>
Allows you to increase or decrease the size of the file I/O
buffers used by the program. The default is 4; values of 1 to 6
may be specified. If you specify too large a value, the program
will abort with a Heap Overflow message. For best performance,
use the largest value that will allow the program to run without
any of the sorts reporting a disk work file has been used.
Example:
BUFFERS 6
Page 8 XLAXNODE II - Version 2.53
PROGRESS
NOPROGRESS
Displays the input filename, zone, region and net number while
the nodelist is being scanned. Using this option with a speech
board will significantly slow things down. NOPROGRESS
suppresses this display. PROGRESS is the default.
CRCCHECK
NOCRCCHECK
Because of widespread misunderstanding of its purpose, this
switch has been renamed to FORCESCAN.
FORCESCAN
NOFORCESCAN
This command controls what happens if your control file does not
request output files. The default, NOFORCESCAN, is for the
program to exit without reading the input nodelist(s).
FORCESCAN causes the input nodelist(s) to be read even if no
output files are requested. They will be checked for correct
syntax and CRC, and the COMMENTS and REPORTS commands will be
processed.
UPDATE command-string
NOUPDATE
Allows you to invoke a nodelist update program (XlaxDiff or
equivalent) before processing begins. Command-string is the full
command, including all arguments, just as you would type it at
the DOS prompt. If the program returns an error code greater
than 1, XlaxNode processing will be aborted. Examples:
UPDATE XlaxDiff /E=D:\NetFiles /C
UPDATE EditNL
Only one UPDATE is permitted. If you have multiple nodelists to
update, you will need to use a batch file to run XlaxDiff before
you invoke XlaxNode.
MAXBAUD nnnn [<flagvalue> <baudrate>]...
Tells the maximum speed of your modem. This value will replace
the speed of any faster nodes. The optional flag pairs specify a
different baud rate to be used if <flagvalue> appears in the
flags field of the nodelist entry. If more than one <flagvalue>
matches a nodelist entry, the last one will be used. Examples:
XLAXNODE II - Version 2.53 Page 9
MAXBAUD 1200 ; All calls limited to 1200
MAXBAUD 2400 HST 9600 ; HST at 9600 others at 2400
MAXBAUD 2400 HST 9600 V32 9600 ; HST and V32 at 9600
Most modern mailers do not need this command. They handle all
modem speed issues in their own control file.
<Flagvalue> only matches COMPLETE flags in the nodelist. V32 will
NOT match a node with a V32b flag.
;PUBLIST [path\]nodelistname
This allows you to override the standard name, NODELIST, for the
input file. Specify an optional drive:path, followed by the 1-8
character file name. Do NOT enter the period or file type. The
program will select the latest list provided you do not have any
files over six months old. Multiple Public lists are NOT
supported. Use ADDLIST for any additional lists, such as
AlterNet or EggNet. Example:
PUBLIST D:\OPUS\FILE\NET\NODELIST
PUBLIST ANETLIST
ADDLIST <filename>...
MYLIST <filename>...
PVTLIST <filename>...
These keywords allow you to specify additional nodelists.
Entries from MYLIST files will be included in the human readable
nodelists. Entries from PVTLIST files will not. By popular
demand, and against my better judgment, FSC-0005 is relaxed to
permit spaces and tabs in these lists.
ADDLIST functions like MYLIST except that the header line with
CRC value is MANDATORY. Use ADDLIST when processing a
distributed nodelist like AnetList or EggList.
Opus 1.0x and Seadog may have problems if net numbers are
duplicated. The NET keyword may be used to modify problem net
numbers.
You may include as many file names as will fit on the line and
use as many of these statements as you wish. Use "###" as the
file type to select the highest numbered nodelist. Example:
ADDLIST ANETLIST.###
PVTLIST POINT1.NET POINT2.NET
Page 10 XLAXNODE II - Version 2.53
Some users may wish to treat zoned nodelists, such as AlterNet or
EggNet, as if they were part of their own zone. This allows
direct calls, without the use of a ZoneGate. This may be done by
prefixing the file name with an exclamation point. This feature
causes the Zones to be changed to Regions in the output file. Be
sure to include ZONE and NET statements to make the required
selections. All references to these nodelists within XlaxNode
(Password, Phone, XPursuit, etc.) MUST refer to the original
zone.
Example:
ADDLIST !ANETLIST.###
NET 7:40
PASSWORD 7:40/0 YOOHOO
Nodelists must be called in the following sequence:
Lists without Zone Statements
Zoned Lists with Region Replacement
Zoned Lists without Region Replacement
ZONE <n> [<n>...]
ONEZONE
GATED
ALLZONES
COMPLETE
The Zone statement selects the zones to be included in the
nodelist. Do not overlook your own zone; it is not included
unless you request it.
For compatibility with earlier versions, OneZone or Gated is
interpreted as "Zone n" where n is the zone you specified in your
NODE statement. Zones 1-255 are supported.
AllZones or Complete is interpreted as "Zone 1 2 ... 255".
Most other nodelist processors automatically include certain
administrative nodes for every zone. XlaxNode normally omits
these nodes to reduce the chances of dialing an international
call by accident. They may be included with the NET command.
Zone Coordinator (n:n/0) records are always selected They cannot
be excluded because of internal housekeeping considerations.
Older software, such as Opus 1.0x and Seadog, does not recognize
zones in the nodelist. The entire nodelist is assumed to be in
your zone. If you use the Zone or AllZones commands to select
another zone, all its nets will be included as if they were in
your zone. This may cause problems with duplicate net numbers.
See the NET statement for a solution.
XLAXNODE II - Version 2.53 Page 11
Newer software, such as Opus 1.1x, Binkley FD and QuickBBS,
supports zones. You may select as many zones as you wish, or
restrict zones to reduce the size of the nodelist.
See the NET command for examples.
NET <zone>:<net> [ <newnumber> | - ]
OZONE <zone>:<net> [ <newnumber> | - ]
The NET command serves several functions. You must always enter
the zone and net number. The zone does not have a default value.
OZONE is accepted for compatibility with other programs.
Listing a zone:net with no other arguments will include the net,
even if its zone has not been requested by the Zone statement.
Listing a zone:net followed by a minus sign will exclude the net,
even if its zone has been requested by the Zone statement.
Listing a zone:net followed by a new net number will include the
net in the output files and alter its number. Opus 1.0x and
Seadog may have problems when net numbers are duplicated. This
option allows you to resolve this conflict.
Example 1:
NODE 1:234/567 ; My Zone is Zone 1.
ONEZONE ; Same as "ZONE 1"
NET 2:2 ; Include Zone 2 Admin Nodes
NET 2:501 ; Also include Net 2:501
Example 2:
NODE 2:345/678 ; My Zone is Zone 2
ZONE 1 2 7 ; Select Zones 1, 2 and 7
NET 1:1200 - ; Exclude Net 1:1200
NET 1:1201 - ; Exclude Net 1:1201
NET 2:50 ; Region 2:50 Independents
NET 3:3 ; Add Zone 3 Admin Nodes
NET 7:500 7500 ; Change 7:500 to 7500
NET 7:630 7630 ; Change 7:630 to 7630
Page 12 XLAXNODE II - Version 2.53
Example 3:
NODE 1:135/990
ZONE ; Don't select ANY zones
NET 1:135 ; Just my own net
NET 1:369 ; and the one next door
IGATE [<zone>:[<net>/]]<node>
OGATE [<zone>:[<net>/]]<node>
GATE [<zone>:[<net>/]]<node>
HUB [<zone>:[<net>/]]<node>
The specified nodes will be marked in the NODELIST.FON files. In
SeaDog modes, they will also be marked in the NODELIST.BBS file.
Network host nodes are always marked as IGATE nodes and Network
hub modes are always marked as HUB nodes. You need to enter
these statements only for nodes that are not marked
automatically. These commands may be repeated.
PHONE [<zone>:[<net>/]]<node> <phonenumber>
Allows you to override a node's phone number. If zone or net is
omitted, your own will be assumed. This statement can be
repeated as required. Entering a phone number for a private node
will cancel the node's private status and host routing. Numbers
entered with the PHONE command do not get listed in the human
readable nodelists.
You should enter the phone number in the exact format as the
numbers in the nodelist. Use the DIAL translation to make any
required alterations to the phone number. Example:
PHONE 135/990 1-305-555-1212
FLAG [<zone>:[<net>/]]<node> <+/=><flagstring>
Allows you to replace or append to a node's flags. If net is
omitted, your net will be assumed. An equal sign replaces a
node's flags, a plus appends to them. You should enter the flags
in the same format as the nodelist. This statement can be
repeated as required. Examples:
FLAG 135/990 +#CM: ; adds #CM: to flags
FLAG 135/990 =HST,MO: ; Changes to HST,MO:
XLAXNODE II - Version 2.53 Page 13
BAUD [<zone>:[<net>/]]<node> <speed>
Allows you to override a node's baud rate. If zone or net is
omitted, your own will be assumed. This statement can be
repeated as required. Example:
BAUD 135/990 56000 ; Waiting for this modem?
PASSWORD [<zone>:[<net>/]]<node> password
Allows you to enter a password into the Nodelist. Passwords are
written to the Old and New Opus Nodelists, the QuickBBS nodelist
and the Binkley Nodelist. OldOpus truncates the password to six
characters, the other nodelists to eight. Like PHONE or BAUD,
this command may be repeated as desired. If you specify a
password for a private node, the program will issue a warning
message and cancel the node's host routing. Example:
PASSWORD 222/1 HotWoc
PASSWORDFILE filename
Provides an alternative method of entering passwords into the
Nodelist. This file is the same format as the OpusNode.PWD file.
Each line has the following format:
[[<zone>:]<net>/]node Password
Example:
333/1 HotWoc
444/2 P42JW9
2:555/1 PW4ME2U ; OldOpus Truncated to six chars
HOSTMARKER <string>
Flags any host routed private and hold nodes by inserting
<string> in front of the node name. Any program that displays
the node name will display this flag. It serves as a warning
that there is no way to send direct transmissions (file requests,
attaches, crash mail) to this node. String may be 1-10
characters and should be omitted to cancel this function.
Example:
HOSTMARKER Host>
HOSTMARKER
The second example cancels host flagging.
The default is the less than symbol (<).
Page 14 XLAXNODE II - Version 2.53
Host flagging can interfere with Seadog 4.5's node name search.
Seadog 4.5 users may wish to cancel this feature.
The V7 nodelist imposes some restrictions on this command. They
are detailed in the description of the VERSION7 command.
DASH
NODASH
The exciting NODASH option strips the dashes out of phone numbers
written to the nodelist files. Some modems get upset if the dial
strings are too long, and this can make them shorter. It also
makes them very difficult to read. DASH is the default. Unlike
Other<tm> programs, XlaxNode knows if a number is domestic or
international, even if the dashes are removed.
MODEMTRANS <bitnum> [!]<flag> [[!]<flag>...]
This command associates strings from the flags field of the raw
nodelist with numeric values in the ModemType field of the
Version6, Version7, and BinkList output files. These numeric
values can be tested by the MODEMTRANS command your Binkley
config file.
<bitnum> is a value from 1 to 7, corresponding to the seven bits
that may be set. <flag> is a nodelist flag such as HST or V32b.
The "!" indicates the flag must not be present.
Multiple flags on the same line are an "AND" condition. Multiple
lines with the same bitnum are an "OR" condition.
Let's consider an example. You have an HST with V32b. Your
first choice is a V32b connect if that's supported. Your next
choice is an HST connect, and your last choice is a V32 connect,
but only if the modem supports MNP, V42, or V42b.
MODEMTRANS 1 V32b
MODEMTRANS 2 HST !V32b
MODEMTRANS 3 V32 !HST MNP
MODEMTRANS 3 V32 !HST V42
MODEMTRANS 3 V32 !HST V42b
If no MODEMTRANS statements are present, the following is
assumed:
MODEMTRANS 1 HST
MODEMTRANS 2 PEP
This default is the value that was hard coded into earlier
versions of the program.
XLAXNODE II - Version 2.53 Page 15
Caution: <Flag> only matches COMPLETE flags in the nodelist. V32
will NOT match a node with a V32b flag.
MODEMSTRING <bitnum> <prefixstring> <suffixstring>
When <bitnum> is set by a MODEMTRANS match for a particular node,
<prefixstring> and <suffixstring> will be inserted before and
after the dialed number.
If a nodes flags set multiple MODEMTRANS bits, only the
MODEMSTRING with the lowest <bitnum> will be used.
For example with the default MODEMTRANS, you may wish to force a
9600 baud connect for HST nodes, and disable VOICE for PEP nodes:
MODEMSTRING 1 &N8DT
MODEMSTRING 2 X4DT
COMMENTS [<filename>]
NOCOMMENTS
Copies any comments contained in the raw nodelist to the
specified file. If the filename is omitted, they will be written
to the XlaxNode report. NOCOMMENTS is the default.
Error messages from the nodelist generation utilities are
inserted into the nodelist as ";E" comments and will be displayed
if COMMENTS is active. Do not be confused by these messages.
They are not XlaxNode errors and there is nothing you can do to
correct them.
REPORT
NOREPORT
Generates a cute little report about how many nodes there are,
how many are down, on hold and private. Since the program
doesn't have any limits on the number of nodes, why do you care?
Default is NOREPORT.
OLDOPUSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ]
VERSION5 [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ]
NOOLDOPUSLIST
For Opus 1.0x. Writes the NODELIST.IDX and NODELIST.SYS files.
NOOLDOPUSLIST is the default. VERSION5 is accepted for
compatibility with ParseLst.
This nodelist file supports true "4D" points. Details are
contained under the heading POINTLISTS.
Page 16 XLAXNODE II - Version 2.53
The PURSUIT subcommands allow you to control the Pursuit script
processing. The default, NOPURSUIT, suppresses script processing
for this nodelist. OLDPURSUIT does the processing for Opus 1.0x,
while NEWPURSUIT does the processing for Opus 1.1x and Binkley.
If you are using Binkley to do all your mail, but wish to share
the nodelist with Opus 1.0x, then the NEWPURSUIT option might be
helpful.
NEWOPUSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ]
VERSION6 [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ]
NONEWOPUSLIST
For Binkley 2.0+ and Opus 1.1x. Writes the NODELIST.IDX and
NODELIST.DAT files. NONEWOPUSLIST is the default. VERSION6 is
accepted for compatibility with ParseLst.
This nodelist file supports true "4D" points. Details are
contained under the heading POINTLISTS.
The PURSUIT subcommands allow you to control the Pursuit script
processing. The default, NOPURSUIT, suppresses script processing
for this nodelist. NEWPURSUIT does the normal processing for
Opus 1.1+ and Binkley, while OLDPURSUIT does the processing for
Opus 1.0x.
I can't think of any reason for doing old style pursuit
processing with this nodelist. Let me know if you do.
VERSION7 [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ]
[ INTERLIST | USERLIST]
NOVERSION7
For Binkley 2.5+ and Opus 1.7x. Writes the NodeX.Dat and .Ndx
files.
This nodelist file supports true "4D" points. Details are
contained under the heading POINTLISTS.
The PURSUIT subcommands allow you to control the Pursuit script
processing. The default, NOPURSUIT, suppresses script processing
for this nodelist. NEWPURSUIT does the normal processing for
Opus 1.1+ and Binkley, while OLDPURSUIT does the processing for
Opus 1.0x.
INTERLIST and USERLIST will create the SYSOP.NDX file. INTERLIST
contains the name of every sysop in the Nodelist, while USERLIST
is confined to those in your zone.
XLAXNODE II - Version 2.53 Page 17
The V7 Nodelist restricts the characters used in the BBS name,
city, and sysop fields to uppercase A-Z and 0-9. Letters will be
made uppercase, and special characters replaced by blanks. The
default HostMarker and PCPMarker strings contain special
characters that are not appropriate for this list.
Your V7 NDX files may be up to 20% smaller than those produced by
other programs. They have all the same information with less
wasted space.
BINKLIST
NOBINKLIST
Writes the NODELIST.IDX and NODELIST.EXT files. NOBINKLIST is the
default. These files provide additional information needed by
Binkley when running with the QuickBBS or TBBS/Seadog files as
the primary nodelist.
QUICKBBSLIST [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ]
NOQUICKBBSLIST
Writes the QuickBBS QNL_DAT.BBS and QNL_IDX.BBS files.
NOQUICKBBSLIST is the default.
The PURSUIT subcommands allow you to control the Pursuit script
processing. The default, NOPURSUIT, suppresses script processing
for this nodelist. NEWPURSUIT does the normal processing for
Opus 1.1x and Binkley, while OLDPURSUIT does the processing for
Opus 1.0x.
I can't think of any reason for doing old style pursuit
processing with this nodelist. Let me know if you do.
QUICKBBSINDEX
NOQUICKBBSINDEX
Writes the QuickBBS 2.75 format NODEINC.DAT and NODEIDX.DAT
files. Except for the file names, these are identical to the
RALIST files. The RA comments and restrictions apply to this
nodelist as well. This format was added based on preliminary
information obtained prior to the release of QuickBBS 2.75, so
the files have not been tested with a production release of
QuickBBS.
Page 18 XLAXNODE II - Version 2.53
RALIST
NORALIST
Writes the NODEIDX.RA and NODEINC.RA files. These are indices to
the raw nodelists. The compiled files contain the filename and
timestamp of the raw nodelist(s), so you must ensure the RA
nodelist directory contains the unaltered input files. XlaxNode
will assign the cost calculated for the /0 node's phone number to
each Zone, Region and Net. This differs from the RANODE practice
of allowing the user to specify these values.
SEADOGLIST
SEADOG45LIST
NOSEADOGLIST
Writes the NODELIST.DOG, NETLIST.DOG and INDEX.DOG files.
NOSEADOGLIST is the default. SEADOG45LIST is for version 4.5 and
later.
CLASS <class> <flagvalue>
This command is used to implement Seadog 4.5 routing classes. It
affects the files produced by the SEADOG45LIST and NODELIST
SEADOG45 commands. <Class> is a single letter routing code that
will be generated for any node with <flagvalue> in the flags
field. Certain class letters are predefined: "H" for any hold
node, "P" for any private node (not host routed by XlaxNode), and
"F" for any node with a fast (over 9600 baud) modem. A node can
have multiple classes. The CLASS statement may be repeated as
many times as desired. Examples:
CLASS C CM
CLASS V V32
<Flagvalue> only matches COMPLETE flags in the nodelist. V32 will
NOT match a node with a V32b flag.
TBBSLIST
NOTBBSLIST
Synonyms for SEADOG.
TPBLIST
NOTPBLIST
Writes the NODELIST.TPB and NETLIST.TPB files. NOTPBLIST is the
default.
XLAXNODE II - Version 2.53 Page 19
FDLIST [ LONGUSER | SHORTUSER ]
NOFDLIST
Writes the FrontDoor 2.0 files. See the heading "FrontDoor
Considerations" for important information about how XlaxNode and
FrontDoor interact. NOFDLIST is the default.
SHORTUSER shrinks the user index by removing multiple listings
for a single name. The "best" node for each name will be
selected. LONGUSER, the default, includes all occurrences of a
name.
XPRESS1
NOXPRESS1
Writes the Silver Xpress XPNLV1.IDX file.
XPRESS2
NOXPRESS2
Writes the Silver Xpress XPNLV2.IDX and XPNLV2.DAT files.
USERLIST [ OPUS | SEADOG | SEADOG45 ]
INTERLIST [ OPUS | SEADOG | SEADOG45 ]
NOUSERLIST
Creates an alphabetical directory of sysops and their node
numbers. USERLIST is restricted to the sysops of nodes selected
by your ZONE and NET commands. INTERLIST includes sysops of all
nodes, selected or not.
OPUS, the default, formats the userlist for use with Opus 1.10
and Binkley. SEADOG formats it for use by Seadog systems prior
to 4.5. The file is named FidoUser.Lst in both these cases.
SEADOG45 is for 4.5 and later. The fill will be named
UserList.Dog and it will contain names of nodes as well as
sysops. Seadog 4.5 users may wish to use the older SEADOG format
to omit node names and save space.
For the Version7 nodelist, the equivalent files are requested as
options of the VERSION7 command.
ADDRLIST filename
This command refers to a personal file of names and node numbers
that will be added to the USERLIST/INTERLIST file. If one of
these names exists in the nodelist, the address specified here
will override the one that would normally be selected.
Page 20 XLAXNODE II - Version 2.53
The file is a standard ASCII text file. Each line has the
following format:
Address_String User_Name_String
Address may be any string up to twenty characters. Seadog allows
non-FidoNet addresses, so the address is not edited. Neither the
address or name field may have any embedded blanks. Example:
1/1 Fido_News
1/1 FidoNews
3:3/0 Zone_Three_Cooord
Palace@EmeraldCity@Oz The_Wizard
ROUTE [ NOPURSUIT | OLDPURSUIT | NEWPURSUIT ]
NOROUTE
Writes NODELIST.FON, the ROUTEGEN work file. Mainly a Seadog
file, rumor has it that this file is sometimes used by non-Seadog
sysops. Default is NOROUTE.
If OLDPURSUIT is selected, the flags field of each Pursuitable
node will have the string "PCPURSUIT" appended. This can be
checked in RouteGen with "FLAG-PCPURSUIT".
If NEWPURSUIT is selected, "PCP-xxxxx" will be appended, where
xxxx is the PCP outdial mnemonic. The general case can be
checked with "FLAG-PCP-". To check a specific city, use "FLAG-
PCP-FLMIA".
NOPURSUIT is the default and suppresses all Pursuit processing
for this file.
NODELIST [ FIDO | OPUS | SEADOG | SEADOG45 ]
NONODELIST
Writes the NODELIST.BBS file. This file is not used by XlaxNode.
There is no need to create it unless it is required as input for
some other nodelist processor. The FIDO, OPUS, SEADOG and
SEADOG45 subcommands select the particular format to be
generated. OPUS and NONODELIST are the defaults.
XLAXNODE II - Version 2.53 Page 21
FIDOPRN
FIDOTXT
FIDODBL
NOFIDOLIST
Gives you a people-readable version of the nodelist. FIDOPRN is
132 columns wide. FIDOTXT is 80 columns wide. FIDODBL is 80
columns wide, but uses two lines per node. The default,
NOFIDOLIST means you don't want any of these disk space hogs.
See the section on PC Pursuit processing for information on how
the contents of these files are modified for Pursuitable nodes.
Also see SINDEX/INDEX and SQUEEZE.
INDEX
SINDEX
NOINDEX
Appends an index to the FIDODBL, FIDOPRN and FIDOTXT lists.
SINDEX is sorted by Zone/Region/Net number, INDEX is in the same
order as the lists. NOINDEX is the default.
NODETEXT [ <headerfilename> [ <trailerfilename> ] ]
NONODETEXT
Another people readable version of the nodelist. This is
formatted for on-line viewing. There are no page breaks or form
feeds. If headerfilename and trailerfilename are specified, these
files are inserted at the start and end of the generated report.
You can insert an introductory message or oANSI control commands.
See the section on PC Pursuit processing for information on how
the contents of this file are modified for Pursuitable nodes.
Also see SQUEEZE.
COORDLIST
NOCOORDLIST
Creates a file named COORD.nnn, where nnn is the number of the
input nodelist. This is a human readable text file listing the
Zone, Region and Net coordinators. Also see SQUEEZE.
SQUEEZE
NOSQUEEZE
Reduces the size of the human readable files by replacing strings
of blanks with tabs. Reductions of 15-35% are typical, as are
similar increases in execution time. NOSQUEEZE is the default.
You may wish to avoid this option if you are using any kind of
program to read the FIDOLIST files. Some programs are confused
if the input file contains tabs.
Page 22 XLAXNODE II - Version 2.53
DELIMITEDFILE [PURSUIT | NOPURSUIT] [FULL | SELECTED]
NODELIMITEDFILE
This is a parsed version of the nodelist formatted for loading
into dBASE, Lotus, Reflex or the like. A detailed file
description is given near the end of this document. The
additional processing triggered by the PURSUIT option is also
described.
If FULL is specified, the file will contain a record for each
node in the input nodelist. SELECTED subjects the output file to
the same Zone/Net selection criteria as the other output files.
COUNTRY <code>
Enter the international telephone prefix for your country. The
default is "1-", for the US and Canada. This must be correct in
order to identify domestic and international numbers.
DIAL <domestic> <international>
It's unlikely that you will be able to use the numbers from the
nodelist exactly as they are. If 1-305-555-1212 is a local call,
the phone company is likely to laugh at you if you try to dial
all 10 digits. Numbers in the nodelist need to be "munged" into
a format acceptable to Mother Bell. The DIAL table is a set of
rules for that job. It starts with a DIAL line, contains zero or
more detail lines, and finishes up with an END statement.
Each detail line in the DIAL table consists of a search part and
a replacement part. The search part of each line is matched
against a node's phone number. As soon as a match is found, the
part matched is replaced, and processing continues with the next
phone number. Assume the following line in the DIAL table:
1-305-555 555 ; Search for "1-305-555" replace with
"555"
If the phone number is 1-305-555-1212, then the 1-305-555 will be
replaced by 555 and the result is 555-1212. This is the normal
format for a local call. You'll probably want a DIAL line like
this for every local prefix.
For long distance within your area code, you probably need to
dial 1 and the seven digit number. After listing all your local
prefixes in the DIAL list, make the following entry:
1-305- 1-
If the 1-305-976 prefix was not individually included in the DIAL
list, then this entry would change 1-305-976-1212 into 1-976-
1212.
XLAXNODE II - Version 2.53 Page 23
If you can dial your entire area code without a 1- prefix, then
you don't need to detail the local exchanges. Just specify:
1-305- /
This will strip the 1-305- from every number in the area code.
For most places, this about covers it. For long distance calls
outside your own area code, you probably dial the number just as
it appears in the nodelist.
Here is an abbreviated version of my DIAL list:
DIAL / 011-/#
1-305-222 222 ; local call
1-305-223 223 ; local call
.
.
.
1-305-939 939 ; local call
1-305 1- ; long distance within 305
END
If you're sharp, you're wondering about the / 011-/# on the DIAL
statement. The entries on the DIAL statement specify what to do
if NONE of the DIAL lines match.
Most North American users can dial other North American numbers
exactly the way they are listed in the nodelist: 1 + AreaCode +
Number. The first slash just serves as a place holder so nothing
gets done to these numbers. For international calls we need to
insert 011- in front of the number. Inserting # at the end of
international numbers speeds completion of the call.
If you're connected to a switchboard that needs 9 before all
local calls, and 8 before all long distance calls, then your
table might look like this:
DIAL 8 8-011/#
1-305-222 9-222 ; local call
1-305-223 9-223 ; local call
.
.
.
1-305-939 9-939 ; local call
1-305- 8-1- ; long distance within 305
END
Suppose that you want to use a dial-up long distance carrier for
those places not listed in your dial list. The following DIAL
statement would do the job:
Page 24 XLAXNODE II - Version 2.53
DIAL 950-1234W9876* 011-
This is saying, if a domestic phone number does not match
anything in the DIAL list, then insert 950-1234W9876* before the
number. International numbers would still get a 011- prefix.
Until now, I've ignored a feature that will not be used by many
people. Besides inserting things before the phone number, you
can append things to the end of phone number. This is where the
slash comes into play. If your long distance company wanted the
security code AFTER the number, the DIAL statement would look
like this:
DIAL 950-1234W/*9876 -011
This says to insert 950-1234W in front of the number and *9876
after the number. When I called the slash a place holder, it was
saying to insert nothing before and nothing after the number.
You can use the slash in a DIAL detail line as well. If you
wanted to use the dial up service within my your area code, then
the line in your DIAL table would look like this:
1-305- 950-1234W/*9876
This would turn 1-305-976-1212 into 950-1234W976-1212*9876.
XLAXNODE II - Version 2.53 Page 25
NOTE!
There is a difference in the way that XLATLIST and XlaxNode
handle dial entries. XLATLIST searches them in the order
entered, so if you had entered:
1-305 1-
1-305-555 555
XLATLIST would NEVER use the second line. XlaxNode sorts them
and always search the longest ones first, so it WOULD find and
use the second line. If you enter strings in a sequence that
will result in output different from XLATLIST, a warning message
will be generated.
As far as the program is concerned, domestic is any number that
has the prefix specified in the COUNTRY statement (defaulting to
1-). Canada, Bermuda, parts of Mexico and the Caribbean Islands
are dialed as domestic calls. You may have 1+ long distance
service from a company that do not handle all these places. If
you are using one of these companies, you will need something
like:
1-809 10288-1-809
to send these calls via AT&T.
COST <dom-cost> <int-cost> [<spec-cost>]
The COST table assigns prices to be charged for Network (Matrix)
mail. It is structured a lot like the DIAL table. It begins
with a COST statement, has one or more detail lines, and finishes
with an END statement.
The COST statement itself accepts three values, the prices for
domestic, international and special nodes. These prices are
defaults for any number that is not listed in the detail section.
Special nodes are private nodes that you have assigned a
password. They cannot be host routed, and there is no phone
number available, so this cost will be used. If omitted, it
defaults to the domestic value.
Lines in the detail section start like lines in the DIAL list,
with a partial phone number to search for. Each search string is
followed by a cost, and an optional baud rate. The baud rate
becomes an upper limit for calls to the numbers specified.
Page 26 XLAXNODE II - Version 2.53
Rather than continue with rules, an example should make it clear.
COST 35 125
1-305-222 0 ; local call
1-305-223 0 ; local call
.
.
.
1-305-939 0 ; local call
1-305 25 ; my own area code.
1-813 25 ; other places in Fla.
1-904 25 ; rest of Fla.
1-809-422 50 1200 ; Nassau
1-809-423 50 1200 ; Nassau
1-809 75 ; Bermuda, Bahamas, Etc.
1-905 90 ; Mexico
1-416 50 ; Ontario Canada
1-514 50 ; Quebec Canada
.
.
.
1-800 0 ; Free Call
END
This first few lines make local E-Mail free. Calls to the rest
of Florida are 25 cents. Calls to Nassau are fifty cents, and no
matter what the speed in the nodelist, I want to call at no more
than 1200 baud. The rest of area 809 is 75 cents. Calls to
Mexico are 90 cents, etc. Any place not mentioned in the list
will be 35 cents if it starts with the 1- prefix, and $1.25
otherwise.
PURSUIT <filename> <cost> <baud> <cxl-string>...
This command defines certain parameters for PC Pursuit
processing. For many sysops, the defaults are satisfactory.
Filename defines the name of the various files used in Pursuit
processing. The default is PCP. In the descriptions that
follow, this filename is assumed. If you use a different name,
you will have to make the necessary adjustments to the names used
in the examples.
The default cost is one cent. Opus 1.03 considers any node with
a zero cost to be a local call. If you have your behavior
windows set up to allow local calls during the day, then Opus
will place daytime Pursuit calls. By setting the cost of a
Pursuit message to a penny, Opus will not consider it a local
call and avoid the high-rent periods.
XLAXNODE II - Version 2.53 Page 27
Opus 1.10 and Binkley allow you to set one value for the price a
user is charged for a message and a different value for call
scheduling purposes. See the remarks under the heading "OPUS
1.1x COST FIELDS".
Baud is the maximum speed to be used for PC Pursuit. You should
set it to 2400 (the default) unless you do not have a 2400 baud
in-dial to Telenet. For any given node, the program will use the
lowest of the node's baud rate, Telenet's outdial rate for the
node's city, the in-dial rate specified here, and MAXBAUD. Even
if this rule sounds clear as mud, it works perfectly.
If Cxl-String appears in a node's flags entry, then Pursuit
processing will be bypassed for that node. This allows you to
bypass Pursuit and dial direct when a node has an HST or PEP
modem. When this string is omitted (the default) all eligible
nodes will be processed. Cxl-String can be repeated as many
times as desired.
You'll need a file called PCP.DAT containing a list of area codes
and exchanges that can be reached via PC Pursuit. A sample
PCP.DAT is included, but Telenet is constantly updating the list.
The basic skeleton of the PCP.DAT file can be downloaded from the
Pursuit bulletin board. Each line begins with an area code,
starting in column one, followed by a list of exchanges within
that area code. Exchanges need not be in sequential order. For
example:
305 222 223 225 229 231 233 235 238
This information should already be in the file when you download
it. Insert a header line in front of each city. It's a standard
ASCII text file, so use your favorite text editor. The header
line consists of the word "NODE" in column one, a space and the
name assigned to the outdial city by Telenet, another space and
the maximum outdial baud for that city. This example indicates
the outdial D/DCWAS supports 2400 baud (1200 is assumed).
NODE D/DCWAS 2400
The Washington outdial node handles calls for area 202 and parts
of 301 and 703. You should list all three area codes under a
single header:
NODE D/DCWAS 2400
202 xxx xxx xxx xxx xxx xxx
202 xxx xxx xxx xxx xxx xxx
301 xxx xxx xxx xxx xxx xxx
301 xxx xxx xxx xxx xxx xxx
703 xxx xxx xxx xxx xxx xxx
703 xxx xxx xxx xxx xxx xxx
Page 28 XLAXNODE II - Version 2.53
The New York outdial node serves 212 and 718, but you must dial
1-718 before calls to the latter. In this case you have a PREFIX
statement:
NODE D/NYNYO 2400
212 xxx xxx xxx xxx
212 xxx xxx xxx xxx
PREFIX 1-718-
718 xxx xxx xxx xxx
718 xxx xxx xxx xxx
The sample file included should make this clear.
Any line that does not start with an area code or the words NODE
or PREFIX will be treated as a comment line. The sample file
uses semi-colons, but almost anything could have been used.
For OLDPURSUIT processing, you will need PCP.INP, a skeleton
script file used to create scripts for reaching each Pursuit
outdial city. The specialized scripts will have file names
PCP.1, PCP.2, etc.
The PCP.INP file is an Opus dialer script with two modifications.
Special markers indicate where the outdial node and the special
area-code prefix must be dialed. When the script is customized,
the outdial node from the NODE statement will be inserted. If
there is an area-code prefix, then it will be inserted as well.
The two spots where these prefixes are to be inserted are
indicated by statements starting in column one:
<<<NODE>>>
<<<PREFIX>>>
The <<<NODE>>> statement causes the program to insert a line
like:
XMIT NYNYO
into the output script. The <<<PREFIX>>> statement causes a line
like:
XMIT 1-718-
to be generated if needed. If not, it will be suppressed.
For NEWPURSUIT processing, you will need PCP.S12 for 1200 baud
calls and PCP.S24 for 2400 baud calls. XlaxNode does not use
these files or even verify they exist. They will be used by Opus
or Binkley when you place a call to one of these nodes.
DIAL processing is very generalized, and works based on string
matches. In order to work with international phone numbers, it
makes no assumptions about their format or punctuation.
XLAXNODE II - Version 2.53 Page 29
PURSUIT processing is just the opposite. It works only with
North American format phone numbers. The number must look like
"1-NNN-NNN-NNNN". They must be exactly fourteen characters long,
start with a "1" and have three hyphens where indicated. The
other characters must all be numbers, and the middle digit of the
area code must be a zero or a one. Any number not meeting these
criteria is not eligible for Pursuit processing.
How does PC Pursuit Processing interact with DIAL processing? An
area code/prefix that you fully specify in the DIAL list will
take priority over the Pursuit entry. A DIAL entry consisting of
a shorter string will NOT take priority over the Pursuit entry.
What if you live in a Pursuitable city? You don't want to use
Pursuit to make local calls. Assume both prefixes are listed in
PCP.DAT, but 305-555 is local and 305-976 is long distance. You
probably have the following DIAL lines:
1-305-555 555
1-305 1
The DIAL entry that matches 555 is nine characters long, so it
would be used, and the call would not be placed with Pursuit.
The DIAL entry that matches the 976 number is less than nine
characters long, so the Pursuit processing takes priority.
There are a few locales that do not require a prefix when dialing
long distance calls within your own area code. You probably have
a single DIAL line to strip the 1- and area code from all numbers
in your area code. You will need to disable your own city in the
PCP.DAT file. Change the baud rate in the NODE statement to zero
to disable a city.
Suppose you want to bypass Pursuit and use your Super-56000 baud
modem for a specific number? Use the following command:
XPURSUIT 1:135/990
Pursuit processing will be bypassed for this node. You can use
as many XPURSUIT commands as you wish.
Pursuitable nodes will be marked by inserting a ">" character in
front of the node's name. This symbol will be displayed by any
program that uses the nodelist files to obtain a nodename. You
may alter or suppress the flag with the following command:
PCPMARKER string
where string is 1-10 characters that will be used to mark PCP
nodes. If string is omitted, no flagging will be done. Note the
restrictions on the PCPMarker that are included in the V7
nodelist.
Page 30 XLAXNODE II - Version 2.53
In addition, the human readable lists will have the PCP node name
inserted in front of the node's city. The NODELIST.FON file will
have the word "PCPURSUIT" added to the flags field.
- NOTES -
The sample PCP script files included with XlaxNode are not
represented as working scripts. They are intended to give you an
idea of how scripts are constructed. I don't have a PC Pursuit
account and I am unable to provide any support for writing or
debugging PCP scripts. Please seek assistance from PCP Gurus on
the PURSUIT BBS, the Pursuit Echo, or the support echo for your
BBS/Mailer.
It is simply not practical for me to try to keep the PCP exchange
lists current, so I won't try. You'll need to get a current
exchange list from the PC-Pursuit BBS.
PCPLIST
NOPCPLIST
PCPLIST causes a file named PCP.PCP to be written. This file is
a compressed version of the data contained in PCP.DAT file. The
program PCP, supplied with XlaxNode, uses this file. NOPCPLIST
is the default, and the file is suppressed.
PRIVATE, HOLD and DOWN NODES
The following discussion does not apply to FrontDoor users, since FD
handles these special cases itself.
Down nodes are omitted from the output files. Private and hold nodes
will inherit the phone number, baud rate, flags and password for their
host. For points, this can be their bossnode, net hub, or net host.
For nodes in a net, this is their hub or host. For independent nodes,
this is their RC.
The bottom line for all this is that your mailer should be able to
call their host and deliver the mail. See the HOSTMARKER command for
an additional feature.
If you place a password on a private node, XlaxNode suppresses this
host routing. If your mailer called the host with the private node's
password, the host would reject the call. If you place a password on
a private (or hold) node, XlaxNode will warn you that the node's mail
must be placed on hold for pickup. You may also use a PHONE statement
to insert the node's number. This will cancel the node's private
status.
XLAXNODE II - Version 2.53 Page 31
Conversely, if you have a password for a node's host, but not for the
node itself, your entry for the node will contain the host's password.
If the node calls you, it will not have the correct password, and your
mailer will reject the call.
EXTENDEDCOST FIELDS
The Version 6 and 7 nodelists have provisions to maintain two cost
fields for each node. One is the cost charged the user for each
message sent. The other is used in the event scheduler to control
when calls can be placed. This allows you more flexibility, since
your charging and routing no longer have to use the same cost. You
can allow users to send free messages to Pursuitable nodes, but
specify a cost that prevents daytime calls.
Every place that XlaxNode allows a cost to be entered, you may enter
two values, separated by a colon. The first value is the traditional
message cost. The second is the call cost for event scheduling
purposes. If you omit the second cost, it defaults to the message
cost. You may enter these values in the COST header line, COST
detail lines, and the Pursuit COST field. Example:
PURSUIT PCP 0:1 ; Free to users but no calls during day
COST 0:25 150 ; Generous Sysop gives free domestic mail
1-305-596 1:0 ; Charge users a penny for local E-Mail
FRONTDOOR CONSIDERATIONS
This version of XlaxNode produces files compatible with FrontDoor
1.99b and later. It will not work with earlier versions. There are
several things to keep in mind when using XlaxNode instead of
FrontDoor's FDNC and Setup programs.
FD handles session passwords by having the Setup program modify the
PASSWORD.SYS file. Recompiling the nodelist with FDNC has no affect
on this file. XlaxNode recreates the PASSWORD.SYS file from the
passwords in your control file; passwords entered with Setup will be
lost. You may prefer to ignore the PASSWORD.SYS file created by
XlaxNode and do all your password maintenance with Setup.
Page 32 XLAXNODE II - Version 2.53
POINTLISTS
A number of the newer mailers support points directly, without the use
of Fakenets. XlaxNode allows an extension to the input nodelist
format that supports points. It's expected that this extension will
soon become a Fidonet standard. Points are entered in the nodelist
directly following their bossnode. Each one starts with the POINT
keyword, followed by the point number. Example.
Host,135,....
....
,990,Friends_of_Dorothy,Miami_FL,Scott_Samet,...
Point,1,The_Emerald_Palace,Over_the_Rainbow,The_Wiz,...
Point,2,...
Point,3,...
Points can appear in any of the input nodelists (PUBLIST, PVTLIST,
MYLIST), but they are written only to these output files:
FDLIST
VERSION5
VERSION6
VERSION7
They are not written to any other output files; they are simply
ignored. You should also be aware that some programs that use the V5
and V6 nodelists will not recognize or support points.
A word of caution. If the zone, region, host or boss node entries
appear in both the main nodelist and a pointlist, you should make sure
that both locations contain accurate data. Otherwise, you may find
that your mailer is using the wrong entry.
Points do not need to have published phone numbers. If the phone
number field is empty or starts with a "-" (as in "-Unpublished-"),
the node will be considered private, and routed via its bossnode.
DELIMITED FILE
The delimited file is a version of the nodelist formatted to import
easily into dBase, Lotus, Reflex or (gag) a BASIC program. There is
no selection for this file. It contains records for every node in all
of the input files, including MYLIST files, unless the SELECTED
keyword is used.
Each node is a single line, consisting of a list of fields separated
by commas. Strings are enclosed in quotes.
XLAXNODE II - Version 2.53 Page 33
NODELIST.DBF, a sample database definition for dBase-III is included.
The commands USE NODELIST and APPEND NODELIST.DLM DELIMITED will load
this database. You may wish use the MODIFY STRUCTURE command to
shorten some of the field lengths before loading. For Lotus, use the
command "File Import Numbers". Allow a LONG time and a LOT of memory.
If you rename the file to type "PRN", the Reflex2 Translate command
will accept this file as type "TEXT". All you need to do is supply
field names.
The fields, in order, are:
Keyword: Will contain one of the following: "ZONE", "REGION",
"HOST", "HUB", "PVT", "HOLD" or "". "" is a normal node.
Down nodes are not included in the file.
Zone: an integer.
Region: an integer.
Net: an integer.
Node: an integer.
Node Name: a quoted string.
Sysop's Name: a quoted string.
City: a quoted string.
Node Phone: phone number as it appears in the nodelist, a quoted
string. Private nodes will have "-Unpublished-" in this
field.
For Hold or Private nodes, the remaining fields refer to the host's
(hub, net, region, zone) information. For normal nodes, they contain
the node's own information.
Dial Phone: phone number after dial translation, a quoted string.
Baud: an integer.
Pursuit City: if Pursuit processing enabled and node is dialable
via Pursuit, the outdial city, in quotes. Otherwise "".
CM: continuous mail indicator, the letter T or F, not quoted.
Flags: a quoted string.
Page 34 XLAXNODE II - Version 2.53
This example has been wrapped to fit the format of this document. In
the file, it occupies a single line.
"ZONE",55,55,0,"Peanut Net","Grand Peanut",
"Plains, GA","1-404-555-1212","1-404-555-1212",1200,
"GAATL",T,"XP,CM:"
CAPACITY
XlaxNode has no limit on the size of the nodelist that it can process.
Its use of memory is quite dynamic, and it's hard to say how much
memory is required. For a small control file with BUFFERS 1, it will
run in 150K. Substantial control files (including full PC Pursuit
processing) with the default BUFFERS value may take 250k.
The options that invoke the sort (VERSION7, SEADOGLIST, FDLIST,
INTERLIST, USERLIST and SINDEX), will add to the time and memory
requirements. All sorts attempt to process the entire file in memory,
but will overflow to EMS or disk if required.
The XlaxNode.Cfg file used by older versions of the program is no
longer needed. You may delete the file.
BUGS, PROBLEMS, COMPLAINTS, SUGGESTIONS and COMPLIMENTS
There is NO repeat NO telephone support. If you need telephone
support, you need a different product.
If you have a problem with the software, do ALL the following:
If running any kind of network, multitasker, or TSR, try the problem
in a stand alone environment. The prime rule is "If I can't reproduce
the problem I can't fix it."
If you are running any kind of odd hardware or old operating system
(MS-DOS version 2.1), try to get a friend to run it on a more common
configuration.
If you are having trouble with Pursuit scripts, you are on your own.
I don't use Pursuit, and have no way to debug a script. The scripts
provided are examples and I don't pretend they will run on your
system.
If you need to file a bug report:
Provide the version number of XlaxNode you are running.
XLAXNODE II - Version 2.53 Page 35
Include the type of machine (IBM PS/50, Homemade AT clone), the name
(MS-DOS, PC-DOS) and version number of your operating system.
Provide the total memory size and the amount of available memory
displayed by ChkDsk or Mapmem. I may have to restrict my memory to
recreate the problem.
Redirect the program's output to a file:
XlaxNode > Error.Rpt
Create an archive that contains a copy of your control file (don't
forget included files), any private nodelists, plus any other
information you think may be germane to the error. If you are worried
about confidential information (passwords and unlisted phone numbers),
overstrike them with X's. Do not remove any statements.
Make YOUR node number part of the archive name so I don't have to
figure out where XlaxNode.Ctl came from.
Send a netmail message with the appropriate supporting files to Scott
Samet at 1:135/990. If you are not listed in the current FIDONET
nodelist, include your data number in the message.
Page 36 XLAXNODE II - Version 2.53
INDEX
ADDLIST ...................... 9 OLDOPUSLIST .................. 15
ADDRLIST ..................... 19 ONEZONE ...................... 10
ALLZONES ..................... 10 OPERATION .................... 6
BAUD ......................... 13 OZONE ........................ 11
BINKLIST ..................... 17 PASSWORD ..................... 13
BUFFERS ...................... 7 PASSWORDFILE ................. 13
BUGS ......................... 34 PCPLIST ...................... 30
CAPACITY ..................... 34 PCPMARKER .................... 29
CLASS ........................ 18 PHONE ........................ 12
COMMANDS ..................... 7 POINTLISTS ................... 32
COMMENTS ..................... 15 PRIVATE NODES ................ 30
COMPLAINTS ................... 34 PROBLEMS ..................... 34
COMPLETE ..................... 10 PROGRESS ..................... 8
COMPLIMENTS .................. 34 PURSUIT ...................... 26
COORDLIST .................... 21 PVTLIST ...................... 9
COST ......................... 25 QUICKBBSINDEX ................ 17
COST FIELDS .................. 31 QUICKBBSLIST ................. 17
COUNTRY <code> ............... 22 RALIST ....................... 18
CRCCHECK ..................... 8 REPORT ....................... 15
DASH ......................... 14 ROUTE ........................ 20
DELIMITED FILE ............... 32 SEADOG45LIST ................. 18
DELIMITEDFILE ................ 22 SEADOGLIST ................... 18
DIAL ......................... 22 SINDEX ....................... 21
DOWN NODES ................... 30 SORTWORK ..................... 7
ERROR CODES .................. 6 SQUEEZE ...................... 21
FDLIST ....................... 19 SUGGESTIONS .................. 34
FIDODBL ...................... 21 TBBSLIST ..................... 18
FIDOPRN ...................... 21 TPBLIST ...................... 18
FIDOTXT ...................... 21 UPDATE ....................... 8
FLAG ......................... 12 USERLIST ..................... 19
FORCESCAN .................... 8 VERSION5 ..................... 15
FRONTDOOR CONSIDERATIONS ..... 31 VERSION6 ..................... 16
GATE ......................... 12 VERSION7 ..................... 16
GATED ........................ 10 WARRANTY ..................... 4
HOLD NODES ................... 30 XPRESS1
HOSTMARKER ................... 13 NOXPRESS1 .................... 19
HUB .......................... 12 XPRESS2
IGATE ........................ 12 NOXPRESS2 .................... 19
INCLUDE ...................... 7 XPURSUIT ..................... 29
INDEX ........................ 21 ZONE ......................... 10
INTERLIST .................... 19
LICENSE ...................... 4
MAXBAUD ...................... 8
MODEMTRANS ................... 14
MYLIST ....................... 9
NET .......................... 11
NEWOPUSLIST .................. 16
NODE ......................... 7
NODELIST ..................... 20
NODETEXT ..................... 21
OGATE ........................ 12